Skip to content

Conversation

trgeiger
Copy link
Contributor

Description

When the move was made to use helm charts for the Tilt configuration, the TLS components were not added. This means in the current state, both operator-controller and catalogd will exit on launch due to metrics-bind-address requiring the tls-key and tls-cert. This PR adds the certManager option to fix this issue.

Reviewer Checklist

  • API Go Documentation
  • Tests: Unit Tests (and E2E Tests, if appropriate)
  • Comprehensive Commit Messages
  • Links to related GitHub Issue(s)

@trgeiger trgeiger requested a review from a team as a code owner September 23, 2025 21:38
Copy link

netlify bot commented Sep 23, 2025

Deploy Preview for olmv1 ready!

Name Link
🔨 Latest commit 72df38b
🔍 Latest deploy log https://app.netlify.com/projects/olmv1/deploys/68d3140d5152c200081c4542
😎 Deploy Preview https://deploy-preview-2233--olmv1.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

The tls flags are required if metrics-bind-address is set. Adding the
certManager option to the tilt.yaml chart makes Tilt work again.

Also fixed a couple spelling errors.
Copy link

codecov bot commented Sep 23, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.84%. Comparing base (16d1089) to head (72df38b).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2233      +/-   ##
==========================================
- Coverage   72.16%   71.84%   -0.33%     
==========================================
  Files          85       86       +1     
  Lines        8440     8474      +34     
==========================================
- Hits         6091     6088       -3     
- Misses       1948     1984      +36     
- Partials      401      402       +1     
Flag Coverage Δ
e2e 39.14% <ø> (+0.03%) ⬆️
experimental-e2e 46.13% <ø> (-0.04%) ⬇️
unit 56.92% <ø> (-0.23%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@anik120 anik120 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good when it comes to just Tilt, but I'm confused because cert-manager is set to enabled:false here

Is our deploy target broken currently in that case? How are the e2es passing?

@dtfranz
Copy link
Contributor

dtfranz commented Sep 24, 2025

Looks good when it comes to just Tilt, but I'm confused because cert-manager is set to enabled:false here

Is our deploy target broken currently in that case? How are the e2es passing?

This file you linked is the most basic set of values we use to deploy v1, on top of which we would set values to change deployment environment, for instance upstream and downstream, the latter of which has certmanager disabled. When we install v1 through upstream make targets, certmanager is enabled because all of the deployment variations use the helm/cert-manager.yaml file, which sets that flag to true.

@dtfranz
Copy link
Contributor

dtfranz commented Sep 24, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 24, 2025
@tmshort
Copy link
Contributor

tmshort commented Sep 24, 2025

This file you linked is the most basic set of values we use to deploy v1, on top of which we would set values to change deployment environment, for instance upstream and downstream, the latter of which has certmanager disabled. When we install v1 through upstream make targets, certmanager is enabled because all of the deployment variations use the helm/cert-manager.yaml file, which sets that flag to true.

Exactly, helm allows us to combine multiple files together to create different manifests.

@tmshort
Copy link
Contributor

tmshort commented Sep 24, 2025

/approve

Copy link

openshift-ci bot commented Sep 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tmshort

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 24, 2025
@tmshort
Copy link
Contributor

tmshort commented Sep 24, 2025

Interesting, we used to have a tilt CI, but it seems to have disappeared?
We do... why isn't it running?
https://github.com/operator-framework/operator-controller/blob/main/.github/workflows/tilt.yaml

@tmshort
Copy link
Contributor

tmshort commented Sep 24, 2025

Hmmm... it didn't run in this PR, but it does run (and pass) in others (#2213)

@openshift-merge-bot openshift-merge-bot bot merged commit 6332ae3 into operator-framework:main Sep 24, 2025
24 checks passed
@dtfranz
Copy link
Contributor

dtfranz commented Sep 24, 2025

Looks like it ran on PR creation, but not on merge?
https://github.com/operator-framework/operator-controller/actions/runs/17959781940

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants